Browse: 🏠 · Solutions · Connectors · Methods · Tables · Content · Parsers · ASIM Parsers · ASIM Products · Logic Apps · 📊
On a Microsoft Sentinel incident, collects File and Host entities, uploads files to Azure Blob Storage via the ANYRUN-Submit-File-to-Blob child playbook, and detonates them in ANY.RUN Sandbox on an Ubuntu environment. Adds analysis comments and uploads IOCs to Threat Intelligence.
| Attribute | Value |
|---|---|
| Type | Playbook |
| Solution | ANYRUN |
| Source | View on GitHub |
This playbook uses 6 Logic App connectors / built-in actions:
| Connector / Action | Type | Connections | Actions |
|---|---|---|---|
azureblob |
Managed | 1 | 1 |
azuresentinel |
Managed | 1 | 9 |
keyvault |
Managed | 1 | 1 |
function |
Built-in | 0 | 1 |
http |
Built-in | 0 | 3 |
workflow |
Built-in | 0 | 1 |
azureblob (Managed)| Action | Method | Endpoint | Other |
|---|---|---|---|
| Get_blob_content_(V2) | get | /v2/datasets/@{encodeURIComponent(encodeURIComponent(variables('Storage Account Name')))}/files/@{encodeURIComponent(encodeURIComponent('/',variables('Container Name'),'/',item()['fileName']))}/content |
— |
azuresentinel (Managed)| Action | Method | Endpoint | Other |
|---|---|---|---|
| Entities_-_Get_Hosts | post | /entities/host |
— |
| Add_comment_to_incident_-_Analysis_Started | post | /Incidents/Comment |
— |
| Update_incident_-_Add_Tags_to_Incident_File | put | /Incidents |
— |
| Threat_Intelligence_-Upload_Indicators_of_Compromise(V2)_-_Malicious_IOCs | post | /V2/ThreatIntelligence/@{encodeURIComponent(triggerBody()?['workspaceId'])}/UploadIndicators/ |
— |
| Threat_Intelligence_-Upload_Indicators_of_Compromise(V2)_-_Suspicious_IOCs | post | /V2/ThreatIntelligence/@{encodeURIComponent(triggerBody()?['workspaceId'])}/UploadIndicators/ |
— |
| Add_comment_to_incident_(V3)_-_ANY.RUN_Output | post | /Incidents/Comment |
— |
| Add_comment_to_incident_(V3)_-_Clean_Scan_File_ANY.RUN_Output | post | /Incidents/Comment |
— |
| Add_comment_to_incident_(V3)_-_entities_uploaded_with_error | post | /Incidents/Comment |
— |
| Add_comment_to_incident_(V3)_-_Entity_is_empty | post | /Incidents/Comment |
— |
keyvault (Managed)| Action | Method | Endpoint | Other |
|---|---|---|---|
| Get_secret_-_ANYRUN | get | /secrets/@{encodeURIComponent('ANYRUN-APIKey')}/value |
— |
function (Built-in)| Action | Method | Endpoint | Other |
|---|---|---|---|
| ANYRUN-Sentinel-FA_Ubuntu_File_Analysis | — | — | functionId=[concat('/subscriptions/', subscription().subscriptionId, '/resourceGroups/', resourceGroup().name, '/providers/Microsoft.Web/sites/', variables('connectFunctionAppName'), '/functions/ANYRUN-Sentinel-FA')] |
http (Built-in)| Action | Method | Endpoint | Other |
|---|---|---|---|
| HTTP-CheckFile-Result | GET | https://api.any.run/v1/analysis/monitor/@{variables('UUID')} |
— |
| HTTP-Full-JSON-Report | GET | https://api.any.run/v1/analysis/@{variables('UUID')} |
— |
| HTTP-GetIOC | GET | https://api.any.run/report/@{variables('UUID')}/ioc/json |
— |
workflow (Built-in)| Action | Method | Endpoint | Other |
|---|---|---|---|
| ANYRUN-Submit-File-to-Blob | — | — | workflowId=[concat('/subscriptions/', subscription().subscriptionId, '/resourceGroups/', resourceGroup().name, '/providers/Microsoft.Logic/workflows/', parameters('Child Logic App Name'))]triggerName= When_a_HTTP_request_is_received |
📄 Source: Sandbox-File-Ubuntu/readme.md
Note: This playbook is required only if you need to analyze files from Ubuntu endpoints and you do not have Microsoft Defender for Endpoint (MDE).
If you have MDE, use the Sandbox-File-Defender playbook instead. It collects files directly via MDE Live Response and does not require the child playbook.
When a Microsoft Sentinel incident is created, this playbook:
Submit-File-to-Blob to upload the file from the endpoint to Azure Blob Storage.ANYRUN-Sentinel-FA.Shared prerequisites (Key Vault secret ANYRUN-APIKey, App Registration, API permissions, role assignments, and Storage Account) are described in the solution README.
Additional requirements for this playbook:
ANYRUN-Sentinel-FA must be deployed in the same subscription and resource group.Submit-File-to-Blob must be deployed first. Note its name — you will enter it as the Child Logic App Name parameter.Click below to deploy Parent Azure Logic App with Flex Consumption plan

Enter the parameters required for deploying the Logic App and click Review + create.
Description of the required parameters:
| Parameter | Description |
|---|---|
| PlaybookName | Logic App name (default ANYRUN-Sandbox-File-Ubuntu). |
| Azure Tenant ID | Tenant ID for authentication in connections. |
| Azure Client ID | Client ID of the App Registration created for the solution. |
| Azure Blob Storage Account Name | Storage account used to store files before they are submitted to ANY.RUN. |
| Azure Blob Storage Container Name | Container name in the storage account. |
| Azure Blob Storage Connection String | Connection string of the storage account. |
| Child Logic App Name | Name of the deployed Submit-File-to-Blob Logic App (default ANYRUN-Submit-File-to-Blob). |
| functionAppName | Name of the deployed Function App. |
After deployment, open the Logic App and authorize the API connections created by the template:
Edit each connection, sign in, and save.
Submit-File-to-Blob to upload the file from the endpoint to Azure Blob Storage.To generate an SAS token for Azure Blob Storage, you need to assign the appropriate role directly to the Logic App.
Open your Storage Account.
Navigate to Access Control (IAM) and click Add.

Specify the child Logic App ANYRUN-Submit-File-to-Blob.
Select the following role:
| Name | Description |
|---|---|
| Storage Account Contributor | Lets you manage storage accounts, including accessing storage account keys which provide full access to storage account data. |
[Content truncated...]
Browse: 🏠 · Solutions · Connectors · Methods · Tables · Content · Parsers · ASIM Parsers · ASIM Products · Logic Apps · 📊